Strange problem... What do you think about the suggestion it does itself?

If you believe you received this message in error, try re-running with 'cargo -- install-update -i cargo-web'

I think Cargo was designed for interactive use and not enough thought put into automated usage. But I don't get why cargo install-update wasn't found after installing cargo-update.

See nabijaczleweli/cargo-update#68

Great that this is fixed. Why then do we want this PR merged?

An hour ago? Sorry, I didn't see harm in it 😄

Oops, misread. I think masking errors with || true is not optimal, so this seems better to me.

🙄 the whole "install an update command just to do an update" thing is not optimal, i.e. we want to update cargo-web if necessary but not reinstall every time (with cargo install --force) because it takes ages (it was suggested we could download the binaries instead, but I view that more as a workaround). cargo install XX || true seems to be the only way to get naive Cargo to do an install only if not already installed.

Does this make Travis time worse? Revert otherwise?

$ cargo install --force cargo-update just took 288s (nearly 5min): https://travis-ci.org/rust-lang-nursery/rand/jobs/356282613